Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@stream-chat-android-compose/src/test/kotlin/io/getstream/chat/android/compose/viewmodel/channels/ChannelListViewModelTest.kt`:
- Around line 485-494: The test's QuerySorter<Message> captor can't capture a
null sort argument; update the capture to allow nulls or assert with a null
matcher. Replace argumentCaptor<QuerySorter<Message>>() with a nullable captor
argumentCaptor<QuerySorter<Message>?>() (or change the verify call to use sort =
isNull()) when verifying chatClient.searchMessages(..., sort = ...), then keep
assertNull(sortCaptor.firstValue) to correctly assert the null messageSearchSort
in ChannelListViewModelTest.
- Around line 417-427: The test uses an argumentCaptor<String>() named captor to
capture the two calls to ChatClient.searchMessages (in ChannelListViewModelTest)
but capture() won't match a null `next` argument; replace with a nullable
capture or verify calls separately: either use captureNullable() (from
mockito-kotlin) on the captor so captor.firstValue can be null, or split into
two verifications of searchMessages (one verifying next == null and the other
verifying next == "cursor_page2") to avoid relying on capture() matching null.
Update the verify block referencing searchMessages, captor, and the assertions
accordingly.

In
`@stream-chat-android-ui-components/src/test/kotlin/io/getstream/chat/android/ui/viewmodels/search/SearchViewModelTest.kt`:
- Around line 115-125: The test uses a non-null argumentCaptor for the nullable
`next` parameter, causing incorrect capture of null values; update the captor
declaration in SearchViewModelTest (the `captor` used in the verify of
`chatClient.searchMessages`) to a nullable captor by using
`nullableArgumentCaptor<String>()` or `argumentCaptor<String?>()` so the `next`
parameter can properly capture null and non-null values for the assertions.

---

Outside diff comments:
In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/viewmodel/channels/ChannelListViewModel.kt`:
- Line 356: In ChannelListViewModel inside the loadMoreQueryMessages logging
call, the logger currently prints the literal text 'query' instead of the
variable; update the logger.v lambda to interpolate the actual query variable
(e.g., use $query or ${query} in the message) so the runtime value of the query
is logged; ensure you reference the correct variable name used in the
surrounding function (loadMoreQueryMessages / query) and keep the existing log
prefix "[loadMoreQueryMessages]" unchanged.

---

Nitpick comments:
In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/viewmodel/channels/ChannelListViewModel.kt`:
- Line 372: The current use of channelLimit as the limit for message searches
(the val limit = channelLimit used before calling searchMessages) causes message
search page size to be tied to channel pagination; fix this by introducing a
dedicated messageSearchLimit (or a local constant) and use that when calling
searchMessages instead of channelLimit—update ChannelListViewModel (where
searchMessages is invoked) to reference messageSearchLimit (or a new constant)
so channelLimit remains only for channel pagination.

In
`@stream-chat-android-ui-components/src/main/kotlin/io/getstream/chat/android/ui/viewmodel/search/SearchViewModel.kt`:
- Around line 160-167: handleSearchMessagesError currently logs and clears
loading flags but leaves SearchState.canLoadMore and next untouched; to prevent
loadMore() from retrying the same failed page, update handleSearchMessagesError
to also set _state.value = _state.value!!.copy(isLoading = false, isLoadingMore
= false, canLoadMore = false) and reset next if desired (e.g., next = null) so
downstream loadMore() won't retry the failed request; locate this logic in the
handleSearchMessagesError function and modify the SearchState copy to include
canLoadMore and optionally next.